Automation objects for integrated design environments

ABSTRACT

The present disclosure is directed to systems, methods and devices for facilitating object-based cross-domain industrial automation control. An object library comprising a plurality of objects may be maintained. One or more of the objects may represent physical counterparts for use in an industrial automation process. Each object of the plurality of objects in the object library may have at least one property that an automated control device operation can be programmed to act on. Each object of the plurality of objects may also have at least one property that a human machine interface component can utilize in generating display elements corresponding to the objects for display on the human machine interface. When modifications to objects in the object library are received, those modifications may be automatically deployed and incorporated in controller logic and HMI graphics and control.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S. Pat.No. 11,119,463, granted on Sep. 14, 2021, entitled AUTOMATION OBJECTSFOR INTEGRATED DESIGN ENVIRONMENTS, and which is hereby incorporated byreference in its entirety.

BACKGROUND

Two of the core features of an industrial automation process are theindustrial controller, which employs controller logic to controlhardware components utilized in the automation process, and the humanmachine interface (HMI), which generates near real-time graphicaldisplay elements corresponding to the hardware components and materialsused in the automated routines. Entities frequently modify operationsthat are performed during automated processes (e.g., to make a processmore efficient, to make a different product, to make a modified product,etc.), as well as the hardware that implements those operations. Whensuch modifications are made, a software engineer typically has to modifyat least one file corresponding to the controller code, and at least onefile corresponding to the HMI code, to ensure that the operationaland/or hardware modifications are properly integrated in the industrialautomation system. Furthermore, when modifications to the controllercode and the HMI code are not properly synced, issues may arise in thecontrol of the industrial automation hardware and/or HMI graphics.

It is with respect to this general technical environment that aspects ofthe present technology disclosed herein have been contemplated.Furthermore, although a general environment has been discussed, itshould be understood that the examples described herein should not belimited to the general environment identified in the background.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription section. This summary is not intended to identify keyfeatures or essential feature of the claimed subject matter, nor is itintended to be used as an aid in determining the scope of the claimedsubject matter.

Non-limiting examples of the present disclosure describe systems,methods, and devices for facilitating object-based cross-domainindustrial automation control. An object library comprising a pluralityof objects may be maintained and accessed by various industrialautomation applications. Each of the plurality of objects maintained inthe object library may have at least one property that an automatedcontrol device operation can be programmed to act on, and at least oneproperty that a human machine interface (HMI) component can utilize ingenerating display elements corresponding to the objects for display onan HMI. In some examples, the plurality of objects may have one or moreadditional properties related to automation system analytics, deviceconfiguration, security (e.g., role-based policy), documentation (e.g.,PDF, JPEG, MIME types), historical logs (e.g., sample period, triggers,calculated values), alarms, batch (e.g., recipe, batch-specificattributes), visualization (e.g., screens, pop-ups), routines, and/ortags. As such, a single object in the object library may be utilized byan industrial control application (a first domain) to, for example,integrate an object type, and logic for controlling that object type, inan automated routine. The same object may be integrated in an HMIapplication (a second domain) for displaying a graphical representationof that object and interacting with hardware components associated withthe object in the automated routine. When objects are removed, added,and/or modified in the object library, those changes can beautomatically deployed to the automated control application files andHMI application files that incorporate the objects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an exemplary distributed computingenvironment for facilitating object-based cross-domain industrialautomation control.

FIG. 2 is a simplified block diagram of an exemplary automation softwareobject and its various components, which may be utilized in the controland visualization of industrial automation processes.

FIG. 3 is a simplified block diagram of an exemplary environment forupdating industrial controller logic and an HMI deployment in responseto modifying a shared object.

FIG. 4 illustrates an exemplary method for facilitating object-basedcross-domain industrial automation control.

FIG. 5 illustrates another exemplary method for facilitatingobject-based cross-domain industrial automation control.

FIG. 6 is a block diagram illustrating example physical components(e.g., hardware) of a computing device with which aspects of thedisclosure may be practiced.

FIG. 7 is a block diagram illustrating physical components (e.g.,hardware) of a computing device with which aspects of the disclosure maybe practiced.

DETAILED DESCRIPTION

Various embodiments will be described in detail with reference to thedrawings, wherein like reference numerals represent like parts andassemblies throughout the several views. Reference to variousembodiments does not limit the scope of the claims attached hereto.Additionally, any examples set forth in this specification are notintended to be limiting and merely set forth some of the many possibleembodiments for the appended claims.

Generally, the present disclosure is directed to systems, methods anddevices for facilitating object-based cross-domain industrial automationcontrol. An object library comprising a plurality of automation objectsthat have instances of compiled counterparts in various hardwarecomponents of the industrial automation system may be maintained. Theobject library may be accessible to industrial automation applications,including industrial control applications (applications for building,modifying, and implementing industrial controller logic), HMIapplications (applications for building HMI graphics and controllingautomated routines via HMI graphics), and industrial routine testingapplications. Software objects in the object library may have layersand/or properties that are shared amongst the various industrialautomation applications. For example, an object for a specific objecttype implemented in an automated process (e.g., a specific type of pump,belt, valve, or sensor utilized in an automated routine) may havephysical properties and/or documentation associated with it that can beutilized by the industrial control application types as well as the HMIapplication types. As such, it is not necessary to create multiplesoftware objects for each hardware object in an automated routine (e.g.,a first software object does not need to be created for the controllerapplication types, with a corresponding second software object having tobe created for the HMI application types). Similarly, when modificationsto objects are made, those modifications are automatically deployed tothe HMI application types and the controller application types ratherthan having to modify two or more objects corresponding to eachapplication or application type.

The current disclosure provides technical advantages over priorsolutions. For example, computer processing costs (CPU cycles) arereduced through implementation of the current invention because the needto create two separate software objects for a single physical componentof an industrial automation process is done away with. That is, separatesoftware objects representing a hardware object for both the HMIapplication environment and the control application environment is nolonger necessary, as a single object, which is executable by bothapplication types, is disclosed herein. The same is true for otherapplication types and documents that software objects may be applied toand/or integrated in (e.g., testing applications, documents of varioustypes). Processing costs are also saved due to only a single set ofmodifications needing to be applied when, for example, a new hardwarecomponent is added, removed, or modified in an automated routine. Thosechanges may be applied to a single object in the object library andautomatically deployed to both the HMI application environment and thecontrol application environment, rather than having to make the samemodifications to two separate objects. Storage costs are also reduced bythe mechanisms described herein, as it is unnecessary to store differentsoftware objects corresponding to a same hardware object for both theHMI application environment and the control application environment.Additionally, the cost to end-user time and resources is reduced byeliminating the need to manually edit and deploy each application typewhen modifications are made to object-type components therein. Rather,according to mechanisms described herein, software objects that can berepresented in each of a plurality of application types may besimultaneously deployed to each of the plurality of application typeswhen modifications are made at the object level without requiring manualmodifications.

FIG. 1 is a schematic diagram of an exemplary distributed computingenvironment 100 for facilitating object-based cross-domain industrialautomation control. Computing environment 100 includes automatedindustrial process software build sub-environment 101, machineautomation lines sub-environment 112, HMI targets sub-environment 120,and controllers sub-environment 128. Any and all of the computingdevices with regard to the various distributed computing environmentsdescribed herein may communicate with one another via one or more wiredor wireless networks. In some examples, controller sub-environment 128,machine automation lines sub-environment 112, and/or HMI targetssub-environment 120, may be deployed together in an industrialautomation process factory setting, such as in factory 113 in deploymentenvironment

Automated industrial process software build sub-environment 101 includescontrol program builder application 102, HMI builder application 104,and test application 106, although other industrial automationapplications are contemplated. Automated industrial process softwarebuild sub-environment 101 also includes object library 108, whichcomprises a plurality of automated software objects that one or more ofthe applications in industrial process software build sub-environment101 may share and/or access. In some examples, object library 108 may bestored locally on one or more computing devices associated with any ofcontrol program builder application 102, HMI builder application 104and/or test application 106. In other examples, object library 108 maybe located remotely (e.g., in cloud storage), and one or more computingdevices executing control program builder application 102, HMI builderapplication 104, and/or test application 106, may access object library108 via a wired or wireless network.

Control program builder application 102 comprises an application forbuilding industrial automation software modules (e.g., single automationcontrol device files, multiple automation control device files) forexecution by one or more industrial controllers (e.g., industrialcontroller—A 130, industrial controller—B 132, industrial controller—C134) in the performance of routines of an automated industrial process.In some examples, the industrial automation software modules that may bebuilt using control program builder application 102 may comprise ladderlogic, function block diagram, sequential function chart, structuredtext, instruction list, C, and C++, among other software forms.

A ladder logic software module may comprise one or more ladder logicstatements, referred to as rungs or instructions. The ladder logicstatements define relationships between an output variable and one ormore input variables. Input variables are variables that correspond tosignals at input terminals and output variables are variables thatcorrespond to signals at output terminals. In relay ladder logic, theinput and output signals may be represented graphically as contactsymbols and coil symbols arranged in a series of rungs spanning a pairof vertical power rails. A typical ladder logic statement may indicatethat a specific output variable is “on” if and only if a first andsecond input is “on”. The ladder logic software module, executed by oneor more industrial controllers, manipulates single-bit input and outputdata representing the state of sensing and operating devices, such asdevices machine automation lines sub-environment 112 (e.g., machine lineA 114, machine line B 116, machine line C 118) in a factory setting. Theladder logic software module, executed by the one or more industrialcontrollers, also performs arithmetic operations, timing and countingfunctions and more complex processing operations. As noted above,however; a controller logic may be created in other software languages,and at its core, the logic functions by taking in inputs from fielddevices, performing calculations and operations on those inputs, andwriting outputs for controlling the field devices based on thecalculations.

HMI builder application 104 is an application for building industrialautomation software modules (e.g., single HMI configuration files,multiple HMI configuration files) for execution on HMI devices in HMItargets sub-environment 120, which may include typical HMI devices suchas dedicated HMI panels, as well as deployment of automationvisualization interfaces on computing devices such as smart phones andtablets. An HMI typically receives, via one or more controllers, andprocesses the status data from devices performing various routines in anindustrial automation process (e.g., devices in machine automation linessub-environment 112, which are deployed in factory 113). An HMIprocesses, utilizing one or more industrial automation software modulesbuilt in HMI builder application sub-environment 104, the status data togenerate various graphical displays, which may indicate the current andhistorical performance of the machines. For example, an HMI graphicaldisplay might indicate status metrics of a drive, the pressure of apump, the speed of a motor, or the output of a robot, each of which maybe performing operations that are part of a routine executed in machineautomation lines sub-environment 112, controlled from one or moreindustrial controllers in controllers sub-environment 128.

Test application 106 may perform one or more operations associated withloading industrial automation software modules into virtualizedindustrial controllers and running one or more industrial automationroutines encoded as instructions in the software modules on thevirtualized industrial controllers. Test application 106 may utilize theproperties of various objects from object library 108 employed in theexecution of one or more routines to determine whether new industrialautomation software controller modules created in control programbuilder application 102 perform as desired. Test application 106 mayalso utilize the properties of various objects from object library 108employed in the execution of one or more routines to determine whethernew industrial automation software HMI modules created in HMI builderapplication 104 perform as desired. If bugs or unintended issues arisein the testing of one or more routines, test application 106 mayidentify an object and or software module associated with the problemand flag it for review.

The industrial controllers in controllers sub-environment 128(industrial controller—A 130, industrial controller—B 132, andindustrial controller—C 134) are special purpose computers used forcontrolling factory devices performing one or more routines in machineautomation lines sub-environment 112. Under the direction of one or moreindustrial automation software modules (e.g., industrial automationsoftware modules built by control program builder application 102), aprocessor of an industrial controller examines a series of inputsreflecting the status of a controller process or device and changesoutputs affecting control of the controlled process or device. Theindustrial controllers in controllers sub-environment 128 may beconstructed in modular fashion to accommodate different applicationtypes requiring different numbers and types of input/output (I/O)circuits as is determined by the particular device or process beingcontrolled.

Industrial automation software modules may be delivered to theindustrial controllers in source format, token format, object code orexecutable code. These modules can bind to and use hardware, firmwareand/or operating system resources of the industrial controllers.Loadable libraries may be provided to the industrial controllers duringruntime to extend functionality and/or provide desired fixes. The storedindustrial automation software modules run in real-time or nearreal-time to provide outputs to the control processes as electricalsignals to outputs such as actuators and the like. The outputs are basedon the logic of an industrial automation software module and inputsreceived from sensors of a controlled process being performed in machineautomation lines sub-environment 112 in a factory such as in factory113. One or more industrial controllers may be involved in theperformance of routines in machine automation lines sub-environment 112,and the industrial controllers involved in those routines maycommunicate with the various devices performing those routines via localconnections, such as by ethernet, or over a wireless network.

One or more of the industrial controllers in controllers sub-environment128 may comprise programmable logic controllers (PLCs), which execute aseries of operations that are performed sequentially and repeatedly. Ingeneral, the series of operations includes an input scan, aprogram/module scan and an output scan. During the input scan the PLCexamines the on or off state of the external inputs and saves thesestates temporarily in memory. During the program/module scan the PLCscans the instruction of the program/module and uses the input status todetermine if an output will be energized. The output results are thensaved to memory. During the output scan the controller will energize orde-energize the outputs based on the output results stored in memory tocontrol the external devices.

The computing devices in computing environment 100 utilizeobject-oriented programming techniques. Additionally, the varioussub-environments in computing environment 100 may utilize shared objectprogramming techniques whereby objects in object library 108, and theobjects' properties, are shared amongst software modules (e.g., HMIsoftware modules in HMI targets sub-environment 120, controller softwaremodules in controllers sub-environment 128). Object oriented programmingshifts the emphasis of software development away from functiondecomposition and towards the recognition of units of software called“objects” which encapsulate both data and functions. Object orientedprogramming objects are software entities comprising data structures andoperations on data. Together, these elements enable objects to modelvirtually any real-world entity in terms of its characteristics,represented by its data elements, and its behaviors represented by itsdata manipulation functions. In this way, objects can model concretethings like physical components of automated industrial processes (e.g.,pumps, belts, filters, tanks, computers), and they can model abstractconcepts like numbers or geometrical concepts (e.g., flow rate values,tank volumes, connection types).

Each object in object library 108 may comprise a set of data (e.g.,attributes) and a set of operations (e.g., methods), that can operate onthe data. Each object in object library 108 may additionally oralternatively comprise a set of renderings that can display a set ofdata, self-describing documentation, one or more graphs that traceobject data, and/or a set of configurations that provide alarms relatedto the data. Methods in an object are invoked by passing a message tothe object. The message specifies a method name and an argument list.When the object receives the message, code associated with the namedmethod is executed with the formal parameters of the method bound to thecorresponding values in the argument list. Methods and message passingin object oriented programming are analogous to procedures and procedurecalls in procedure-oriented software environments.

However, while procedures operate to modify and return passedparameters, methods operate to modify the internal state of theassociated objects (by modifying the data contained therein). Thecombination of data and methods in objects is called encapsulation.Encapsulation provides for the state of an object to only be changed bywell-defined methods associated with the object. When the behavior of anobject is confined to such well-defined locations and interfaces,changes (e.g., code modifications) in the object will have minimalimpact on the other objects and elements in the system.

Each object in object library 108 represents a class of some controlelement. A class includes a set of data attributes plus a set ofallowable operations (e.g., methods) on the data attributes. Objectoriented programming supports inheritance—a class (called a subclass)may be derived from another class (called a base class, parent class,etc.), where the subclass inherits the data attributes and methods ofthe base class. The subclass may specialize the base class by addingcode which overrides the data and/or methods of the base class, or whichadds new data attributes and methods. Thus, inheritance represents amechanism by which abstractions are made increasingly concrete assubclasses are created for greater levels of specialization. One or moreobjects in object library 108 may comprise complex objects built frommultiple instances of similar objects. Systems, methods and devicesdescribed herein may employ abstract object classes, which are designsof sets of objects that collaborate to carry out a set ofresponsibilities. Frameworks are essentially groups of interconnectedobjects and classes that provide a prefabricated structure for a workingapplication. Additional description related to the objects and theirimplementation in the current invention is provided in relation to FIG.2 .

FIG. 2 is a simplified block diagram of an exemplary automation softwareobject 200 and its various components, which may be utilized in thecontrol and visualization of industrial automation processes androutines. Object 200 is an automation software object that may beincluded as part of a software object library, such as object library108. In some examples, object 200 may be incorporated in controllersoftware modules for execution by one or more industrial controllers forcontrolling operations associated with automated industrial processesand routines, and/or virtualized industrial controllers for virtuallycontrolling operations associated with automated industrial processesand routines. In additional examples, object 200 may be incorporated inHMI software modules for execution by one or more HMIs for generatingvarious graphical displays, which may indicate the current andhistorical performance of the machines associated with automatedindustrial processes and routines. In additional examples, object 200may be incorporated in both HMI software modules and controller softwaremodules.

Object 200 comprises a class type 202. While various class types arepossible for assignment to object 200, for exemplary purposes, object200 is indicated as having one of a sensor class type 204, a valve classtype 206, or a pump class type 208 assigned to it. The class typesdepicted in the object class type 202 element each correspond to acommon hardware type in industrial automation processes, and they areprovided for exemplary purposes; however, users may also create theirown class types, which may correspond to combinations of product typesand/or product skids (e.g., combinations of devices for performingvarious automation routines). Additionally, although broad class typesare shown for ease of example, each class type may have sub-class typesas well (e.g., specific types of sensors, valves, pumps, controllers,displays, etc.), for which more exact specifications may be associatedwith object 200.

Object 200 also includes collaboration layer 210, test layer 212,controller layer 214, and visual layer 216. Controller layer 214comprises a plurality of properties and property types, includingphysical properties 218, documentation properties 220, and compatibilityproperty type 222. In some examples, controller layer 214 may alsocomprise controller code and/or properties.

Documentation properties 220 may include information about the specificobject type specified in object class type 202. For example, if object200 is a specific brand and type of valve, documentation properties 220may specify the name of the manufacturer of the valve, actions that maybe performed by the valve, operating pressures that the valve canwithstand, operating temperatures that the valve can withstand, flowrate, etc. If object 200 is a specific brand and type of temperaturesensor, documentation properties 220 may specify the name of themanufacturer of the sensor, temperature range of the sensor, accuracyrange of the sensor, scan frequency of the sensor, etc. If object 200 isa specific brand and type of pump, documentation properties 220 mayspecify the name of the manufacturer of the pump, maximum discharge flowfor the pump, maximum discharge pressure for the pump, operatingtemperatures that the pump can withstand, horsepower for the pump, etc.

Compatibility properties 222 may also include information about thespecific object type specified in object class type 202. For example, ifobject 200 is a specific brand and type of valve, compatibilityproperties 222 may specify types of service the valve is intended tohandle (e.g., air, gas, liquid, vacuum), connection types, etc. Ifobject 200 is a specific brand and type of temperature sensor,compatibility properties 222 may specify types of environments it isintended to handle (e.g., air, gas, liquid, vacuum), connection types,etc. If object 200 is a specific brand and type of pump, compatibilityproperties 222 may specify types of service the pump is intended tohandle (e.g., types of fluid), connection types, etc.

Physical properties 218 include the physical specifications (e.g., size,geometry, mass, material etc.) of object 200.

Visual layer 216 includes display properties, which in association withone or more physical properties 218, documentation properties 220,and/or compatibility properties 222, may be utilized to accuratelygenerate display components in real-time corresponding to componentsoperating in an industrial automation routine. For example, displayproperties 224 may include various color properties for types of liquidand gas in an industrial automation routine, and when data from pumps,sensors and tanks from the routine are processed by the HMI and/or anindustrial controller, those physical properties may be translated withthe appropriate color types for the liquid and/or gas involved in theroutine for graphically displaying the current state of the routine.

Controller layer 214 comprises a plurality of industrialcontroller-oriented operations/methods that may be performed by anindustrial controller utilizing one or more properties of object 200,such as physical properties 218, documentation properties 220,compatibility properties 222, and/or display properties 224 (inassociation with visual layer 216). The operations performed by theindustrial controller utilizing instructions associated with controllerlayer 214 direct hardware components of industrial automation processesto perform actions associated with ladder logic routines via various I/Ocommunications as more fully described above.

Test layer 212 comprises a plurality of industrial controller-orientedoperations/methods that may be performed by a virtual industrialcontroller utilizing one or more properties of object 200. The testlayer may be associated with the performance of test script operationson object 200 that a typical industrial controller would be expected toperform, while flagging failed operations or operations that lead tounexpected results. Test layer 212 may also include a plurality ofHMI-oriented operations/methods that may be performed by an HMI orvirtualized HMI utilizing one or more properties of object 200,including display properties 224, physical properties 218, documentationproperties 220, and/or compatibility properties 222.

Collaboration layer 210 comprises a plurality of operations/methods thatmay be performed on one or more properties of object 200. Thecollaboration operations/methods permit multi-user access to a controlproject, including centralized control, message coding from one user toanother, collaborative development of industrial automation projects,such as collaborative development of application code for an industrialcontroller or design of an industrial automation process system.According to some examples, operations associated with collaborationlayer 210 may provide mechanisms for users to leave notes for oneanother in association with objects and/or industrial automationprojects that objects are included in. In additional examples, theoperations associated with collaboration layer 210 may providemechanisms for users to flag issues associated with development ofindustrial automation projects. In some examples, the operationsassociated with collaboration layer 210 may provide for cross-domaincollaboration (e.g., a first user may leave a note related to an objectwhile working with the object in HMI code and the note may be surfacedto a second user in relation to the same object in controller code thatthe second user is working on). In other examples, the operationsassociated with collaboration layer 210 may provide for same-domaincollaboration (e.g., a first user may leave a note related to an objectin a first area and/or routine of controller code and the note may besurfaced to a second user in relation to the same object in a secondarea and/or routine of controller code that the second user is workingon).

FIG. 3 is a simplified block diagram of an exemplary environment 300 forupdating industrial controller logic and an HMI deployment in responseto modifying a shared object. Exemplary environment 300 includes objectmodification sub-environment 302, HMI graphics sub-environment 312 andindustrial controller logic sub-environment 316.

Object modification sub-environment 302 includes computing device 308,which is utilizing an industrial automation application to add or modifyautomation object 310. In some examples, the industrial automationapplication utilized to add or modify automation object 310 may compriseindustrial control application 304 and/or HMI application 306.Industrial control application 304 may generally be utilized forcreating and modifying industrial controller logic implemented inindustrial automation processes, and HMI application 306 may generallybe utilized in creating and modifying HMI graphics, and graphicalcommands, related to the execution of industrial automation processes.

Automation object 310, whether it is being modified or newly created viacomputing device 308, is deployed in at least one routine of anindustrial automation process. Automation object 310 is a cross-domainobject, having a visual layer and an controller layer, which has sharedproperties that may be utilized by HMI application 306 to generategraphics corresponding to an industrial automation process thatautomated object 310 is deployed in, and by industrial controlapplication 304 to generate control logic/code corresponding to anindustrial automation process that automated object 310 is deployed in.Automation object 310 may comprise one or more additional layers,including test layer 314 and/or collaboration layer 212, as discussedabove in relation to FIG. 2 .

Automation object 310, whether it is being created or modified, may bestored in an object library, such as object library 108 in FIG. 1 . Inthis example, upon modification or creation, automation object 310 isincorporated in HMI application 306 for use in generating HMI graphicsfor one or more routines that automation object 310 has been associatedwith in object modification sub-environment 302. The incorporation ofautomation object 310 to HMI application 306 is illustrated withreference to computing device 314 in HMI graphics sub-environment 312.As a basic example, if automation object 310 corresponds to a new tankor valve component of a new type, with different specifications, that isreplacing an existing tank or valve component in an existing automatedroutine, the graphical representation of that tank or valve componentwould likewise be modified in its graphical display in HMI application306 due to the modification to automation object 310.

Additionally, in this example, upon modification or creation, automationobject 310 is also incorporated in industrial control application 304for use in modifying the industrial controller logic associated with oneor more routines that automation object 310 has been associated with inobject modification sub-environment 302. In other examples, rather thanmodifying an automation routine due to an object modification, a routinemay simply act on physical hardware corresponding to the modifiedobject. The deployment of automation object 310 to industrial controlapplication 304 is illustrated with reference to computing device 318 inindustrial controller sub-environment 316. As a basic example, ifautomation object 310 corresponds to a new tank or valve component of anew type, with different specifications, that is replacing an existingtank or valve component in an existing automated routine, the ladderlogic for controlling that tank or valve component may likewise also bemodified due to its different specifications compared with thepreviously employed model.

FIG. 4 illustrates an exemplary method 400 for facilitating object-basedcross-domain industrial automation control. The method 400 begins at astart operation and flow moves to operation 402

At operation 402 an object library is maintained. The object library maybe maintained in association with one or more industrial automationapplications (e.g., an industrial control application, an HMIapplication, a test application). In some examples, the object librarymay comprise a cloud-based library that is accessed by one or moreindustrial automation applications via a network. In other examples, theobject library may be stored all or in part on client computing deviceson which the industrial automation applications are running.

From operation 402 flow continues to operation 404 where a modifiedversion of the automation object is received by the object library. Insome examples, receiving the modified version of the automation objectmay comprise receiving a completely new object that replaces apreviously existing automation object in the object library (e.g., a newobject is created that has different properties and/or a differentobject class associated with it than a previously existing automationobject that it is replacing/modifying). In other examples, receiving themodified version of the automation object may comprise receiving amodification to an existing automation object in the library (e.g.,receiving a property value modification to an existing automationobject, changing the object class or sub-class type for an existingautomation object).

From operation 404 flow continues to operation 406 where updatedindustrial controller operations are automatically deployed to a logiccontroller based on the modification to the automation object. In someexamples, the modified object may be automatically deployed, upon itsmodification, to an industrial control application for incorporation inautomated routines that the previous version of the automation objectwas deployed in. In other examples, the modified object may be deployed,when a user explicitly indicates, to an industrial control applicationfor incorporation in automated routines that the previous version of theautomation object was deployed in.

In specific examples, if the modification of the object comprisesspecification modifications for one or more hardware componentsassociated with an industrial automation routine, when the modificationto the automation object is received, controller logic associated withthe previous version of the automation object may be automaticallyupdated to adjust to the modified object. For example, if valvespecifications for a valve object are modified, ladder logic thatincorporates the new valve may be modified to compensate for thatmodification (e.g., size modifications for a valve object may result inflow rate changes in ladder logic, size modification for a valve objectmay result in timing changes in ladder logic).

From operation 406 flow continues to operation 408 where updated displayproperties for the automated object are automatically deployed to an HMIcomponent based on the modification to the automation object. In someexamples, the modified object may be automatically deployed, upon itsmodification, to an HMI application, such as HMI application 306, forgenerating display elements associated with industrial automationroutines, and controlling automated routines from HMI interfaces, thatthe previous version of the automation object was deployed in. Inspecific examples, if the modification of the object comprisesspecification modifications (e.g., size properties, class typeproperties, etc.) for one or more hardware components associated with anindustrial automation routine, when the modification the automationobject is received, HMI graphics for the automation object correspondingto those modified specifications may be automatically updated in the HMIapplication.

In examples where an object being modified does not already exist in anautomated routine, the newly modified object may be available forincorporation into new routines from the object library. For example,when an object from the object library is modified, or a new object isadded to the object library, the object and its properties may becomeavailable for use by a control program builder application, such ascontrol program builder application 102; an HMI builder application,such as HMI builder application 104; and/or a test application, such astest application 106.

From operation 408 flow continues to an end operation and the method 400ends.

FIG. 5 illustrates another exemplary method 500 for facilitatingobject-based cross-domain industrial automation control. The method 500begins at a start operation and flow moves to operation 502.

At operation 502 an object library comprised of a plurality of objectsthat have physical counterparts for use in an automated industrialprocess is maintained. The object library may be maintained inassociation with one or more industrial automation applications (e.g.,an industrial control application, an HMI application, a testapplication). In some examples, the object library may comprise acloud-based library that is accessed by one or more industrialautomation applications via a network. In other examples, the objectlibrary may be stored all or in part on client computing devices onwhich the industrial automation applications are running.

From operation 502 flow continues to operation 504 where a set ofproperties for each object is maintained. The set of properties for agiven object may link that object with an automated control deviceprogramming environment and an HMI environment. For example, physicalproperties, documentation properties, and/or compatibility propertiesassociated with an object may determine how a hardware componentcorresponding to the object can be controlled via an industrialcontroller from an automated control device programming environment,while at the same time, one or more of those same properties may beutilized by an HMI environment for determining which graphical elementsshould be generated by an HMI application for representing the hardwarecomponent.

From operation 504 flow continues to operation 506 where a request toadd an object from the object library into an automated industrialprocess is received. In some examples, the request may be received viaan industrial control application. In other examples, the request may bereceived via an HMI application. In still other examples, the requestmay be received via a test application for testing industrial automationroutines. In some examples, the request may be received via asystem-level tool that integrates the object from the object librarywith each application component that it can be applied in. The requestmay comprise a request to add an entirely new object, corresponding toan entirely new piece of hardware in an automated routine, to theautomated industrial process. For example, the request may correspond toadding an additional tank of a new or existing type to an existingautomated routine. In other examples, the request may comprise a requestto modify an existing object in an automated routine (e.g., replace anexisting tank in a routine with a new tank, replace an existing sensorin a routine with a new sensor).

From operation 506 flow continues to operation 508 where a file forexecuting one or more operations in an automated industrial process byan automated control device is generated based on one or more propertiesassociated with the object in the object library. For example, the file,depending on the object properties of the new object, may be generatedto include various timing information, flow rate information,temperature information, voltage information, etc. incorporated in acontroller logic file for one or more operations of an industrialautomation routine and process that the object is utilized in.

From operation 508 flow continues to an end operation and the method 500ends.

FIG. 6 illustrates one aspect in which an exemplary architecture of acomputing device according to the disclosure that can be used toimplement aspects of the present disclosure, including any of theplurality of computing devices described herein with reference to thevarious figures and their corresponding descriptions. The computingdevice illustrated in FIG. 6 can be used to execute the operatingsystem, application programs, and software modules (including thesoftware engines) described herein, for example, with respect to FIG. 7and program engines 714, joint rendering engine 716, module splittingengine 718, test engine 720, collaboration engine 722, and locationdetermination engine 724. By way of example, the computing device willbe described below as the industrial automation computing device 610. Toavoid undue repetition, this description of the computing device willnot be separately repeated for each of the other computing devicesdescribed herein, but such devices can also be configured as illustratedand described with reference to FIG. 6 .

The computing device 610 includes, in some embodiments, at least oneprocessing device 680, such as a central processing unit (CPU). Avariety of processing devices are available from a variety ofmanufacturers, for example, Intel, Advanced Micro Devices, and/or ARMmicroprocessors. In this example, the computing device 610 also includesa system memory 682, and a system bus 684 that couples various systemcomponents including the system memory 682 to the processing device 680.The system bus 684 is one of any number of types of bus structuresincluding a memory bus, or memory controller; a peripheral bus; and alocal bus using any of a variety of bus architectures.

Examples of computing devices suitable for the computing device 610include a server computer, a programmable logic controller computer, adesktop computer, a laptop computer, a tablet computer, a mobilecomputing device (such as a smart phone, an iPod® or iPad® mobiledigital device, or other mobile devices), or other devices configured toprocess digital instructions.

The system memory 682 includes read only memory 686 and random accessmemory 688. A basic input/output system 690 containing the basicroutines that act to transfer information within computing device 610,such as during start up, is typically stored in the read only memory686.

The computing device 610 also includes a secondary storage device 692 insome embodiments, such as a hard disk drive, for storing digital data.The secondary storage device 692 is connected to the system bus 684 by asecondary storage interface 694. The secondary storage devices 692 andtheir associated computer readable media provide nonvolatile storage ofcomputer readable instructions (including application programs andprogram engines), data structures, and other data for the computingdevice 610. Details regarding the secondary storage devices 692 andtheir associated computer readable media, as well as their associatednonvolatile storage of computer readable instructions (includingapplication programs and program engines) will be more fully describedbelow with reference to FIG. 7 .

Although the exemplary environment described herein employs a hard diskdrive as a secondary storage device, other types of computer readablestorage media are used in other aspects according to the disclosure.Examples of these other types of computer readable storage media includemagnetic cassettes, flash memory cards, digital video disks, Bernoullicartridges, compact disc read only memories, digital versatile disk readonly memories, random access memories, or read only memories. Additionalaspects may include non-transitory media. Additionally, such computerreadable storage media can include local storage or cloud-based storage.

A number of program engines can be stored in secondary storage device692 or memory 682, including an operating system 696, one or moreapplication programs 698, other program engines 600 (such as thesoftware engines described herein), and program data 602. The computingdevice 610 can utilize any suitable operating system, such as Linux,Microsoft Windows™, Google Chrome™, Apple OS, and any other operatingsystem suitable for a computing device.

According to examples, a user provides inputs to the computing device610 through one or more input devices 604. Examples of input devices 604include a keyboard 606, mouse 608, microphone 609, and touch sensor 612(such as a touchpad or touch sensitive display). Additional examples mayinclude other input devices 604. The input devices are often connectedto the processing device 680 through an input/output interface 614 thatis coupled to the system bus 684. These input devices 604 can beconnected by any number of input/output interfaces, such as a parallelport, serial port, game port, or a universal serial bus. Wirelesscommunication between input devices and the interface 614 is possible aswell, and includes infrared, BLUETOOTH® wireless technology, cellularand other radio frequency communication systems in some possibleaspects.

In an exemplary aspect, a display device 616, such as a monitor, liquidcrystal display device, projector, or touch sensitive display device, isalso connected to the system bus 684 via an interface, such as a videoadapter 618. In addition to the display device 616, the computing device610 can include various other peripheral devices (not shown), such asspeakers or a printer.

When used in a local area networking environment or a wide areanetworking environment (such as the Internet), the computing device 610is typically connected to a network through a network interface 620,such as an Ethernet interface. Other possible embodiments use othercommunication devices. For example, certain aspects of the computingdevice 610 may include a modem for communicating across the network.

The computing device 610 typically includes at least some form ofcomputer readable media. Computer readable media includes any availablemedia that can be accessed by the computing device 610. By way ofexample, computer readable media include computer readable storage mediaand computer readable communication media.

Computer readable storage media includes volatile and nonvolatile,removable and non-removable media implemented in any device configuredto store information such as computer readable instructions, datastructures, program engines or other data. Computer readable storagemedia includes, but is not limited to, random access memory, read onlymemory, electrically erasable programmable read only memory, flashmemory or other memory technology, compact disc read only memory,digital versatile disks or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium that can be used to store the desired informationand that can be accessed by the computing device 610. Computer readablestorage media does not include computer readable communication media.

Computer readable communication media typically embodies computerreadable instructions, data structures, program engines or other data ina modulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” refers to a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, computer readable communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, radio frequency, infrared, andother wireless media. Combinations of any of the above are also includedwithin the scope of computer readable media.

The computing device illustrated in FIG. 6 is also an example ofprogrammable electronics, which may include one or more such computingdevices, and when multiple computing devices are included, suchcomputing devices can be coupled together with a suitable datacommunication network so as to collectively perform the variousfunctions, methods, or operations disclosed herein.

FIG. 7 is a block diagram illustrating additional physical components(e.g., hardware) of a computing device 700 with which certain aspects ofthe disclosure may be practiced. The computing device componentsdescribed below may have computer executable instructions for:maintaining an object library comprising a plurality of objects, whereineach of the plurality of objects has at least one property that anautomated control device operation can be programmed to act on, andwherein each of the plurality of objects has at least one property thata human machine interface component can utilize in generating displayelements corresponding to the objects for display on a human machineinterface. Computing device 700 may perform these functions alone or incombination with a distributed computing network one or more additionalcomputing devices which may communicate and process the one or more ofthe program engines in FIG. 7 including joint rendering engine 716,which may perform one or more operations associated with rendering aplurality of software modules corresponding to hardware components of anautomated routine/process as a singular navigable unit; module splittingengine 718, which may perform one or more operations associated withsplitting at least one software module off from a collaborativelyrendered software module unit; test engine 720, which may perform one ormore operations associated with testing ladder logic via one or morevirtual industrial controllers; collaboration engine 722, which mayperform one or more operations associated with allowing users tocommunicate and leave notes for one another in the development ofindustrial automation projects; and location determination engine 724,which may perform one or more operations associated with identifying alocation in a software module that has been affected by a modificationto a first software module.

In a basic configuration, the computing device 700 may include at leastone processor 702 and a system memory 710. Depending on theconfiguration and type of computing device, the system memory 710 maycomprise, but is not limited to, volatile storage (e.g., random accessmemory), non-volatile storage (e.g., read-only memory), flash memory, orany combination of such memories. The system memory 710 may include anoperating system 712 and one or more program engines 714 suitable forfacilitating object-based cross-domain industrial automation control,such as one or more components in regards to FIG. 6 and, in particular,joint rendering engine 716, module splitting engine 718, test engine720, collaboration engine 722, and location determination engine 724.The operating system 712, for example, may be suitable for controllingthe operation of the computing device 700. Furthermore, aspects of thedisclosure may be practiced in conjunction with a graphics library,other operating systems, or any other application program and is notlimited to any particular application or system.

The computing device 700 may have additional features or functionality.For example, the computing device 700 may also include additional datastorage device (removable and/or non-removable) such as, for example,magnetic disks, optical disks, or tape. Such additional storage isillustrated in FIG. 7 by storage 704. It will be well understood bythose of skill in the art that storage may also occur via distributedcomputing networks, which are not shown in FIG. 7 .

As stated above, a number of program engines and data files may bestored in the system memory 710. While executing the processor 702, theprogram engines 714 (e.g., joint rendering engine 716, module splittingengine 718, test engine 720, collaboration engine 722, and locationdetermination engine 724) may perform processes including, but notlimited to, the aspects described herein.

Aspects of the present disclosure, for example, are described above withreference to block diagrams and/or operational illustrations of methods,systems, and computer program products according to aspects of thedisclosure. The functions/acts noted in the blocks may occur out of theorder as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

The description and illustration of one or more aspects provided in thisapplication are not intended to limit or restrict the scope of thedisclosure as claimed in any way. The aspects, examples, and detailsprovided in this application are considered sufficient to conveypossession and enable others to make and use the best mode of claimeddisclosure. The claimed disclosure should not be construed as beinglimited to any aspect, example, or detail provided in this application.Regardless of whether shown and described in combination or separately,the various features (both structural and methodological) are intendedto be selectively included or omitted to produce an embodiment with aparticular set of features. Having been provided with the descriptionand illustration of the present disclosure, one skilled in the art mayenvision variations, modifications, and alternate aspects falling withinthe spirit of the broader aspects of the general inventive conceptembodied in this application that do not depart from the broader scopeof the claimed disclosure.

The various embodiments described above are provided by way ofillustration only and should not be construed to limit the claimsattached hereto. Those skilled in the art will readily recognize variousmodifications and changes that may be made without following the exampleembodiments and applications illustrated and described herein, andwithout departing from the true spirit and scope of the followingclaims.

The invention claimed is:
 1. A system for facilitating object-basedcross-domain industrial automation control, the system comprising: amemory that stores executable components; and a processor, functionallycoupled to the memory, that executes the executable components, theexecutable components comprising: an object library component configuredto: maintain, in an object library, an object comprising a deviceproperty that an industrial control application utilizes to performactions associated with an automated control device, and a visualizationproperty that a human machine interface (HMI) application utilizes togenerate a display element corresponding to the object; and in responseto a modification of a property value of the object, automaticallydeploy a modified version of the object to the industrial controlapplication and to the HMI application; the industrial controlapplication functionally coupled to the object library component andconfigured to: incorporate the modified version into the industrialcontrol application; and generate, based at least on the deviceproperty, control logic for a device operation; and the HMI applicationfunctionally coupled to the object library component and configured to:incorporate the modified version into the HMI application; and generate,based at least on the visualization property, display elementscorresponding to the object.
 2. The system of claim 1, wherein theautomated control device comprises one of: a logic controller, and avirtual controller.
 3. The system of claim 1, wherein the object isdeployed in the industrial control application prior to the modificationof the property value.
 4. The system of claim 1, wherein themodification of the property value comprises an addition of a newfeature to the object into an automated industrial process, and whereinthe industrial control application is further configured to: in responseto the addition of the new feature to the object, generate, based atleast on the device property, a file for execution of at least anoperation in the automated industrial process by the automated controldevice.
 5. The system of claim 4, wherein the HMI application is furtherconfigured to: generate, based at least on the addition of the newfeature to the object, a file for displaying a representation of the newfeature on an automation visualization computing device.
 6. The systemof claim 4, wherein the HMI application is further configured to: enabledisplay, based on the addition of the new feature to the object, of arepresentation of the new feature on an automation visualizationcomputing device, wherein the representation corresponds to thevisualization property.
 7. The system of claim 1, wherein the industrialcontrol application is further configured to, in response to receivingthe modified version from the object library component, automaticallydeploy, based on the modified version, updated controller operations tothe automated control device; and wherein the HMI application is furtherconfigured to, in response to receiving the modified version from theobject library component, automatically deploy, based on the modifiedversion, updated display properties.
 8. A non-transitorycomputer-readable medium having stored thereon instructions that, inresponse to execution, cause a system comprising a processor to executean object library component configured to: maintain, in an objectlibrary, an object comprising a device property that an industrialcontrol application utilizes to perform actions associated with anautomated control device, and a visualization property that a humanmachine interface (HMI) application utilizes to generate a displayelement corresponding to the object; and in response to a modificationof a property value of the object, automatically deploy a modifiedversion of the object to the industrial control application; wherein theindustrial control application is functionally coupled to the objectlibrary component and configured to: incorporate the modified versioninto the industrial control application; and generate, based at least onthe device property, control logic for a device operation; and whereinthe HMI application is functionally coupled to the object librarycomponent and configured to: incorporate the modified version into theHMI application; and generate, based at least on the visualizationproperty, display elements corresponding to the object.
 9. Thenon-transitory computer-readable medium of claim 8, wherein theautomated control device comprises one of: a logic controller and avirtual controller.
 10. The non-transitory computer-readable medium ofclaim 8, wherein the object is deployed in the industrial controlapplication prior to the modification of the property value.
 11. Thenon-transitory computer-readable medium of claim 8, wherein themodification of the property value comprises an addition of a newfeature to the object into an automated industrial process, and whereinthe industrial control application is further configured to: in responseto the addition of the new feature to the object, generate, based atleast on the device property, a file for execution of at least anoperation in the automated industrial process by the automated controldevice.
 12. The non-transitory computer-readable medium of claim 11,wherein the HMI application is further configured to: generate, based atleast on the addition of the new feature to the object, a file fordisplaying a representation of the new feature on an automationvisualization computing device.
 13. The non-transitory computer-readablemedium of claim 11, wherein the HMI application is further configuredto: enable display, based on the addition of the new feature to theobject, of a representation of the new feature on an automationvisualization computing device, wherein the representation correspondsto the visualization property.
 14. The non-transitory computer-readablemedium of claim 8, wherein the industrial control application is furtherconfigured to, in response to receiving the modified version from theobject library component, automatically deploy, based on the modifiedversion, updated controller operations to the automated control device;and wherein the HMI application is further configured to, in response toreceiving the modified version from the object library component,automatically deploy, based on the modified version, updated displayproperties.
 15. A method for facilitating object-based cross-domainindustrial automation control, comprising executing an object librarycomponent configured to: maintain, in an object library, an objectcomprising a device property that an industrial control applicationutilizes to perform actions associated with an automated control device,and a visualization property that a human machine interface (HMI)application utilizes to generate a display element corresponding to theobject; and in response to a modification of a property value of theobject, automatically deploy a modified version of the object to theindustrial control application; wherein the industrial controlapplication is functionally coupled to the object library component andconfigured to: incorporate the modified version into the industrialcontrol application; and generate, based at least on the deviceproperty, control logic for a device operation; and wherein the HMIapplication is functionally coupled to the object library component andconfigured to: incorporate the modified version into the HMIapplication; and generate, based at least on the visualization property,display elements corresponding to the object.
 16. The method of claim15, wherein the automated control device comprises one of: a logiccontroller and a virtual controller.
 17. The method of claim 15, whereinthe object is deployed in the industrial control application prior tothe modification of the property value.
 18. The method of claim 15,wherein the modification of the property value comprises an addition ofa new feature to the object into an automated industrial process, andwherein the industrial control application is further configured to: inresponse to the addition of the new feature to the object, generate,based at least on the device property, a file for execution of at leastan operation in the automated industrial process by the automatedcontrol device.
 19. The method of claim 18, wherein the HMI applicationis further configured to: generate, based at least on the addition ofthe new feature to the object, a file for displaying a representation ofthe new feature on an automation visualization computing device.
 20. Themethod of claim 18, wherein the HMI application is further configuredto: enable display, based on the addition of the new feature to theobject, of a representation of the new feature on an automationvisualization computing device, wherein the representation correspondsto the visualization property.